-
Notifications
You must be signed in to change notification settings - Fork 83
feat(integration-tests): Record required components for the clp package in component_list data member within PackageConfig.
#1658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…ig file; address comments.
…er-level clp-config.yml
…E_CONFIGS other than clp-text and clp-json
…equired components.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
…nning of fixture names.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
component_list data member to PackageConfig data class.component_list data member within PackageConfig.
Description
This PR introduces the
component_listdata member toPackageConfigdata class. The data member is used for tracking which containerized components a given CLP package configuration needs to run.PR dependencies
This PR depends on the following being merged:
clp-textandclp-jsonpackages. #1437Checklist
breaking change.
Validation performed
Ran the following command from
clp/integration-tests:uv run pytest -m 'package'Both the
clp-jsonandclp-texttests passed.